Skip to content

docs: update reactions and targeted messages status from "preview" to "coming soon"#2731

Open
Copilot wants to merge 5 commits intomainfrom
copilot/update-docs-coming-soon
Open

docs: update reactions and targeted messages status from "preview" to "coming soon"#2731
Copilot wants to merge 5 commits intomainfrom
copilot/update-docs-coming-soon

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 30, 2026

Reactions and targeted messages are no longer described as "in preview" — they should be labeled as "coming soon" instead. This update also adds actual API usage examples for reactions across all supported languages, adds messageReaction event handling examples, and removes empty section headings that rendered with no content for TypeScript and Python users.

Changes

  • sending-messages/README.mdx: Updated admonition labels for both Targeted Messages and Reactions sections (:::info[Preview]:::info[Coming Soon]); removed empty ### Targeted messages coming soon and ### Reactions coming soon section headings (which only had content for C#); added reactions-example and reactions-event-example includes to display actual usage snippets
  • sending-messages/proactive-messaging.mdx: Same admonition update for the Targeted Proactive Messages section
  • sending-messages/typescript.incl.md: Added reactions-example section with a TypeScript snippet showing api.reactions.add() and api.reactions.remove(); added reactions-event-example section showing how to handle incoming messageReaction events via app.on('messageReaction', ...)
  • sending-messages/python.incl.md: Added reactions-example section with a Python snippet showing ctx.api.reactions.add() and ctx.api.reactions.delete(); added reactions-event-example section showing @app.on_message_reaction with ctx.activity.reactions_added / ctx.activity.reactions_removed
  • sending-messages/csharp.incl.md: Added reactions-example section with a C# snippet showing context.Api.Reactions.Add() and context.Api.Reactions.Remove(); added reactions-event-example section showing app.OnMessageReaction(...) with context.Activity.ReactionsAdded / context.Activity.ReactionsRemoved; the existing .NET experimental opt-in tip (reactions-preview-note) is preserved and still rendered inline for .NET users

Copilot AI changed the title [WIP] Update documentation for reactions and targeted messages docs: update reactions and targeted messages status from "preview" to "coming soon" Mar 30, 2026
Copilot AI requested a review from heyitsaamir March 30, 2026 16:06
Copy link
Copy Markdown
Collaborator

@copilot I noticed the snippets are not working for TS and Py

Reactions in preview

[Dev] Section "reactions-preview-note" not found in TypeScript documentation. Either mark the section explicitly as N/A for intentionally ignored, or fill in documentation.

This section isn't needed for those languages. But we do need snippets on how actually to use these APIs (use example folder in @microsoft/teams.ts and @microsoft/teams.py)

Copy link
Copy Markdown
Contributor Author

Copilot AI commented Mar 30, 2026

@copilot I noticed the snippets are not working for TS and Py

Reactions in preview<...

Fixed in 9e0ac81:

  1. Added actual reactions-example code snippets to the TypeScript, Python, and C# include files showing how to add/remove reactions via api.reactions.add() / api.reactions.remove() (TS), ctx.api.reactions.add() / ctx.api.reactions.delete() (Py), and context.Api.Reactions.Add() / context.Api.Reactions.Remove() (C#) — sourced from the example apps in @microsoft/teams.ts and @microsoft/teams.py.

  2. Removed the ### Targeted messages coming soon and ### Reactions coming soon section headings that rendered as empty sections for TS and Py. The C# experimental opt-in note (targeted-preview-note / reactions-preview-note) is still rendered inline for .NET users without a misleading heading.

Copy link
Copy Markdown
Collaborator

@copilot can you also include getting reaction events too (messageReaction events)

Copy link
Copy Markdown
Contributor Author

Copilot AI commented Mar 30, 2026

@copilot can you also include getting reaction events too (messageReaction events)

Added in 4fd1fc9. Each language include file now has a reactions-event-example section showing how to handle incoming messageReaction events:

  • TypeScript: app.on('messageReaction', ...) iterating over activity.reactionsAdded and activity.reactionsRemoved
  • Python: @app.on_message_reaction with ctx.activity.reactions_added / ctx.activity.reactions_removed
  • C#: app.OnMessageReaction(...) with context.Activity.ReactionsAdded / context.Activity.ReactionsRemoved

The README now also includes a brief description before the event-handling snippet.

Copy link
Copy Markdown
Collaborator

@corinagum corinagum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coming soon should not be provided without a date. Other thoughts posted in Teams.

@heyitsaamir
Copy link
Copy Markdown
Collaborator

@copilot for targeted messages and reactions, can you say Coming soon in May 2026

…d targeted messages

Agent-Logs-Url: https://github.com/microsoft/teams-sdk/sessions/f79908e6-d4c3-4f01-b24d-deef146520b6

Co-authored-by: heyitsaamir <48929123+heyitsaamir@users.noreply.github.com>
Copy link
Copy Markdown
Contributor Author

Copilot AI commented Apr 2, 2026

@copilot for targeted messages and reactions, can you say Coming soon in May 2026

Done in c5d3f69. Updated the admonition body text in both README.mdx (Targeted Messages and Reactions sections) and proactive-messaging.mdx to read "coming soon in May 2026".

@heyitsaamir heyitsaamir requested a review from corinagum April 2, 2026 01:21
@heyitsaamir heyitsaamir marked this pull request as ready for review April 2, 2026 01:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants